I will painstakingly learn how to use Astro.js (specifically its content collection system and dynamic routing system) to replace my homebrewed code I wrote in about two days using regexes, hacky methods of caching the rendered markdown files, and a complex spaghetti network of functions that technically function but are a giganormous pain to update with new features. I used a master JSON file to easily implement a standardized config for each 'collection' since it allows me the flexibility of simply cloning a new Git repository into the data directory and adding one or more config entries, optionally including a token and setting whether I want to index them or not, and whether the index is of a directory of raw files (eg images, PDFs, assets for download, etc) to a list. Also, I for the rewrite, I decided to use a per-directory yaml file to easily assign IDs and unique authentication tokens to specific files while also essentially symbolically linking them relative to the root of the git repo instead of trying to maintain two copies of the file (useful when hosting schoolwork) since it was a major pain point my previous system had. Before, it just URL encoded the file name (leading to %20 in files with spaces) but now I can assign them specific IDs (very, very useful for organization). The tokens were also collection-wide so if I gave a token to someone, then they could also use it for other shared documents. Astrojs also has a static-site-generation mode where it will completely staticize your entire site so you can deploy it on host-only (eg, no compute services, such as surge.sh). Overall, I learned job-critical skills and optimized the end-to-end experience for users (namely myself) of my homegrown Markdown content hosting platform.